Release 10.1A: OpenEdge Application Server:
Administration

Client connections to the OpenEdge Adapter for SonicMQ

The OpenEdgeAdapter for SonicMQ allows OpenEdge applications to communicate via JMS Messaging through SonicMQ.

OpenEdge Adapter for SonicMQ BrokerConnect (BrokerConnect)

The 4GL client application connects to BrokerConnect by specifying, when the JMS session is created, the connection parameters of either the NameServer (if a controlling NameServer is specified for the adapter) or the adapter itself.

The client can connect in the following ways:

Via HTTP or HTTPS over the Internet, with use of the AppServer Internet Adapter. See Chapter 3, "Configuring and Managing the AppServer Internet Adapter," for more information.
Via AppServer protocol, with or without Secure Sockets Layer (SSL) tunneling. To support SSL communications with client applications, BrokerConnect must be configured as an SSL-enabled server. See the "SSL-enabled BrokerConnect operation" section for more information.

OpenEdge Adapter for SonicMQ ClientConnect (ClientConnect)

ClientConnect is for OpenEdge clients and will run as a background process in conjunction with a Progress 4GL client. There is a single adapter process per client process with the SonicMQ Broker acting as a service point for all JMS sessions.

OpenEdge Adapter for SonicMQ ServerConnect (ServerConnect)

The ServerConnect option is for OpenEdge Application Servers (WebSpeed and AppServer). With this configuration, there is a single adapter process per unified broker process, allowing multiple Application Server agents to connect to this single adapter process.

For information about programming 4GL client applications in the SonicMQ environment, see OpenEdge Development: Messaging and ESB . Also see OpenEdge Getting Started: Application and Integration Services for a discussion of OpenEdge Adapter for SonicMQ architecture.